Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1291

reference: 544-tree-1
name: 1291
tree-preservation-order: undefined
544-tpo-1
uprn
address-text
point: POINT (-1.014808 50.883598)
geometry: MULTIPOLYGON (((-1.014765 50.883594,-1.014767 50.883602,-1.014773 50.883609,-1.014782 50.883616,-1.014807 50.883621,-1.014820 50.883620,-1.014832 50.883616,-1.014842 50.883610,-1.014848 50.883603,-1.014850 50.883594,-1.014848 50.883586,-1.014843 50.883578,-1.014833 50.883572,-1.014821 50.883568,-1.014808 50.883567,-1.014795 50.883568,-1.014783 50.883572,-1.014774 50.883578,-1.014767 50.883585,-1.014765 50.883594)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL